Systems and methods for automatically updating data representative of insurance related information

ABSTRACT

The present disclosure generally relates to systems and methods for automatically updating data representative of insurance related information. In particular, the present disclosure relates to systems and methods for automatically updating data representative of insurance related information based on data, representative of desired updates, entered by a customer and data representative of update rules. The data representative of desired updates may be compared to the data representative of the update rules to generate updates to data representative of insurance related information.

CROSS-REFERENCE TO RELATED APPLICATION

The present application is a continuation of U.S. patent applicationSer. No. 14/152,016, entitled SYSTEMS AND METHODS FOR AUTOMATICALLYUPDATING DATA REPRESENTATIVE OF INSURANCE RELATED INFORMATION, filedJan. 10, 2014, the disclosure of which is incorporated herein in itsentirety by reference.

TECHNICAL FIELD

The present disclosure generally relates to systems and methods forautomatically updating data representative of insurance relatedinformation. In particular, the present disclosure relates to systemsand methods for automatically updating data representative of insurancerelated information based on data representative of desired updates,that is entered by an insurance customer, and data representative ofupdate rules.

BACKGROUND

Currently, data representative of insurance related information, such asinsurance claim information, is manually updated. Typically, aninsurance customer contacts an insurance agent via telephone and conveysupdate information. The insurance agent, in turn, manually updates datarepresentative of the insurance related information based on her ownknowledge and based on the information provided by the insurancecustomer.

For example, an insurance customer may experience a vehicle accident andbe in need of a rental vehicle. The insurance customer may call aninsurance agent to initiate the claim process and to request a rentalvehicle. If the insurance customer's insurance policy provides forrental vehicle coverage, the insurance agent may update datarepresentative of the insurance claim to include associated vehiclerental information. On the other hand, if the insurance customer'sinsurance policy does not provide for rental vehicle coverage, theinsurance agent may inform the insurance customer of the fact and notupdate the data representative of the insurance claim.

Systems and methods are desired that enable an insurance customer toenter updates to data representative of insurance related informationwithout the assistance of an insurance Agent. Moreover, systems andmethods are desired that compare data representative of desired updatesto data representative of insurance related information, entered by aninsurance customer, to update rules and that update the datarepresentative of insurance related information if the datarepresentative of the desired updates satisfies the update rules.

SUMMARY

A computer-implemented method of automatically updating datarepresentative of insurance related information may include receiving,at a processor of a computing device, current data, wherein the currentdata is representative of current insurance related information. Themethod may further include generating, using a processor of a computingdevice, a current display based on the current data, wherein the displaypresents current insurance related information to an insured individual.The method may also include receiving, at a processor of a computingdevice, change data from the insured individual, where the change datais representative of desired change information associated with thecurrent insurance related information. The method may yet furtherinclude receiving, at a processor of a computing device, update rulesdata, wherein the update rules data is representative of rules relatedto updates to the current insurance related information that arepermitted by an insured individual. The method may even yet furtherinclude determining, using a processor of a computing device, whether atleast one change to the current insurance related information isacceptable based on the change data and the update rules data.

In another embodiment, a computer system for automatically updating datarepresentative of insurance related information may include a currentdata receiving module stored on a memory that, when executed by aprocessor of a computing device, causes the processor to receive currentdata, wherein the current data is representative of current insurancerelated information. The computing system may also include a currentdisplay generating module stored on a memory that, when executed by aprocessor of a computing device, causes the processor to generate acurrent display based on the current data, wherein the display presentscurrent insurance related information to an insured individual. Thecomputer system may further include a change data receiving modulestored on a memory that, when executed by a processor of a computingdevice, causes the processor to receive change data from the insuredindividual, where the change data is representative of desired changeinformation associated with the current insurance related information.The computer system may yet further include an update rules datareceiving module stored on a memory that, when executed by a processorof a computing device, causes the processor to receive update rulesdata, wherein the update rules data is representative of rules relatedto updates to the current insurance related information that arepermitted by an insured individual. The computer system may even yetfurther include an acceptable change determining module stored on amemory that, when executed by a processor of a computing device, causesthe processor to determine whether at least one change to the currentinsurance related information is acceptable based on the change data andthe update rules data.

In yet a further embodiment, a tangible computer-readable memory storinginstructions for automatically updating data representative of insurancerelated information may include a current data receiving module that,when executed by a processor of a client device, causes the processor ofthe client device to receive current data from a remote computingdevice, wherein the current data is representative of current insurancerelated information. The instructions may also include a current displaygenerating module that, when executed by a processor of a client device,causes the processor of the client device to generate a current displaybased on the current data, wherein the display presents currentinsurance related information to an insured individual. The instructionsmay further include a change data receiving module that, when executedby a processor of a remote computing device, causes the processor of theremote computing device to receive change data from the insuredindividual via a client device, where the change data is representativeof desired change information associated with the current insurancerelated information. The instructions may yet further include an updaterules data receiving module that, when executed by a processor of aremote computing device, causes the processor of the remote computingdevice to receive update rules data, wherein the update rules data isrepresentative of rules related to updates to the current insurancerelated information that are permitted by an insured individual. Theinstructions may even yet further include an acceptable changedetermining module that, when executed by a processor of a remotecomputing device, causes the processor of the remote computing device todetermine whether at least one change to the current insurance relatedinformation is acceptable based on the change data and the update rulesdata.

BRIEF DESCRIPTION OF THE DRAWINGS

The figures described below depict various aspects of the systems andmethods disclosed herein. It should be understood that each figuredepicts an embodiment of a particular aspect of the disclosed systemsand methods, and that each of the figures is intended to accord with apossible embodiment thereof. Further, wherever possible, the followingdescription refers to the reference numerals included in the followingfigures, in which features depicted in multiple figures are designatedwith consistent reference numerals.

FIG. 1 depicts an example flow diagram for a method of automaticallyupdating insurance related information;

FIG. 2 depicts a high-level block of an example system for automaticallyupdating insurance related information;

FIG. 3 depicts a block diagram of an example client device forautomatically updating insurance related information;

FIG. 4 depicts a flow diagram of an example method of entering desiredupdates to insurance related data representative of insurance relatedinformation;

FIG. 5 depicts a block diagram of an example computing device forautomatically updating insurance related information; and

FIG. 6 depicts a flow diagram of an example method of generating updatesto insurance related data representative of insurance relatedinformation.

DETAILED DESCRIPTION

The systems and methods of the present disclosure provide the abilityfor an insurance customer to update their own information whileprotecting business information of an insurance provider. In particular,the systems and methods of the present disclosure may allow an insurancecustomer to update insurance claim information. The systems and methodsmay be applied to business processing data. Alternatively, the systemsand methods may be applied to customer record management (CRM) datawhich may, otherwise, be updated in place.

Generally, the systems and methods of the present disclosure may presentinformation to an insurance customer that is representative of currentinsurance related data, for example, data representative of a currentinsurance claim related to a vehicle accident. The systems and methodsmay receive desired changes to the current insurance related informationfrom the customer, such as a request for a rental vehicle. The systemsand methods may compare the desired changes, received from the insurancecustomer, to insurance provider rules, such as whether rental vehiclecoverage is included in an associated insurance policy. The systems andmethods may determine whether current insurance related information maybe updated based on a comparison of the desired changes with theinsurance provider rules. The systems and methods may automaticallyupdate the current insurance related information if a determination ismade that the desire changes comply with the rules.

For example, if the insurance customer requests a rental vehicle andinsurance provider rules (e.g., insurance policy coverage) provide forrental vehicle coverage, a current claim may be revised to includerental vehicle information. On the other hand, if the rules (e.g.,insurance policy coverage) do not provide for rental vehicle coverage,the current insurance claim information may not be updated. In eitherevent, the systems and methods of the present disclosure may generate adisplay that indicates the disposition to the insurance customer.Alternatively, if the systems and methods cannot make a finaldetermination, the information may automatically be forwarded to aninsurance agent to conduct a further review.

Turning to FIG. 1, a flow diagram for an example method of automaticallyupdating insurance related information 100 is illustrated. As describedin detail herein, the method 100 may be implemented using the computersystem 200 of FIG. 2. A line with a closed arrow (

) in FIG. 1 generally represents an “is a” relationship. A line with anopen arrow (>) in FIG. 1 generally represents a “uses” relationship. Forexample, loss event 138 “is a” information collector. As anotherexample, loss event 148 “is a” external information update. A screenflow manager 123 and a business process manager 125 are abstractconcepts. Accordingly, an information collection manager 113 “is a”screen flow manager 113 and an external information update manager 115“is a” business process manager 125.

In any event, a processor (e.g., processor 250 of FIG. 2) may implementan information collector 120 to collect data representative ofinformation related to insured property 145 that may, in turn, berepresentative of vehicle information 160 (e.g., automobile information165 or watercraft information 168). The processor 250 may also implementthe information collector 120 to collect data representative ofinformation related to an insured party 143 (e.g., an insurancecustomer). The processor 250 may further implement the informationcollector 120 to collect data related to associated insurance policyinformation 140. The processor 250 may yet further implement theinformation collector 120 to collect data related to a loss event 138(e.g., a claim related to damage due to a vehicle accident). Theprocessor 250 may implement an information collection manager 113 todirect the information collector 120 to collect data related to theinsured property 145, the party 143, the policy 140 and the loss event138. The processor 250 may combine the data related to the insuredproperty 145, the party 143, the policy 140 and the loss event 138 andgenerate current data that is representative of current insurancerelated information.

With further reference to FIG. 1, a processor (e.g., processor 225 ofFIG. 2) may implement an external information update 128 to update datarepresentative of information related to insured property 155 that may,in turn, be representative of vehicle information 155 (e.g., automobileinformation 170 or watercraft information 173). The processor 225,further implementing the external information update 128, may updatedata representative of information related to an insured party 153(e.g., an insurance customer). The processor 225, yet furtherimplementing the external information update 128, may update datarelated to associated insurance policy information 150. The processor225, also implementing the external information update 128, may updatedata related to a loss event 148 (e.g., a claim related to damage due toa vehicle accident). The processor 225 may implement an externalinformation update manager 115 to direct the external information update128 to collect data related to the insured property 155, the party 153,the policy 150 and the loss event 148. The external information updatemanager 115 is, for example, responsible for finding an existinginsurance claim, or delay any update until a claim is created.Furthermore, the external information update manager 115 may ensurefirst-in-first-out (FIFO) manipulation of data. The external informationupdate manager 115 may initiate a task manager services (Claim handlerand customer to do) 118 to perform various tasks. The processor 225 maycombine the data related to the insured property 155, the party 153, thepolicy 150 and the loss event 148 and generate change data that isrepresentative of desired changes desired by an insurance customer tothe current insurance related information.

With yet further reference to FIG. 1, the processor 250 may implement aclaim data access services 110, a screen flow manager 123 and a businessprocess manager 125 to coordinate implementation of the informationcollection manager 113 and the external information update manager 115.For example, the processor 250 may implement the claim data accessservices 110, the screen flow manager 123 and the business processmanager 125, along with implementation of the next steps rules engine133 to determine whether desired insurance related information changes,received from an insurance customer, comply with insurance providerrules (e.g., rules with an insurance policy 140). The processor 250 mayfurther implement a work in progress manager 105 to generate an externalupdate log 108. The external update log 108 may be representative of arecord disposition of a customer update.

As illustrated by dashed-line boxes in FIG. 1, the in process “to do”list 103, the task manager services (Claim handler and customer to do)118 and the next step rules engine 133 may be implemented separate fromthe method 100. For example, the in process “to do” list 103, the taskmanager services (Claim handler and customer to do) 118 and the nextstep rules engine 133 may be implemented as a “customer to do” process.These are items that a customer needs to complete to assist theprocessing of an insurance claim. Some of the items may be identifiedduring a screen flow, such as when another vehicle is involved in aninsurance claim and to provide the other vehicle driver information.Identifying next steps and having an in process customer to do mayfacilitate incorporation of related information into a correspondingscreen flow process. If a client does not have the information, theinformation may be input via a regular customer to do process. The samerules may be applied to “to do” items in a screen flow process asapplied to separate work items to be done later. As further illustratedin FIG. 1 using a dashed-line box, the work in progress manager 105 maybe implemented separate from the method 100 to manage items collectedbut not yet processed. The progress manager 105 may form a connectionbetween the information collection manager 113 and external informationupdate manager 115. The external information update manager 115 may alsouse the work in progress manager 105 to see other work waiting and toensure first-in-first-out (FIFO).

With even further reference to FIG. 1, the processor 250 may furtherimplement the external information update 128 to access an automaticupdate engine 130 and a claim data update service 135 to generate datarepresentative of whether change data, representative of desired changesto current insurance information, comply with rule data that isrepresentative of insurance provider rules (e.g., rules within aninsurance policy).

As a specific example, the processors 225, 250 may implement, at leastportions of, the method 100 to allow an insurance customer to create ormodify a vehicle rental reservation. Generally, a vehicle rental may berequested once an associated loss has been submitted. However a vehiclerental cannot be sent to a vendor until a claim has been created and acause of loss (COL) has been created and a rental performer assigned.Creation of a COL may indicate that insurance coverage exists and mayalso set reserves. The processor 250 may determine that a vehicle rentalis not valid on a duplicate claim. Furthermore, the associated claimmust be in an open status. The processor 225 may allow an insurancecustomer to select a vehicle rental branch and date of pick up from acorresponding display and submit the request. The processor 250 may logthe request in the work in progress and start the handle rental requestprocess. Generally, a rental branch and vehicle type cannot beautomatically changed by a client once the rental vehicle has beenpicked up. However, in accordance with blocks 635, 640 of FIG. 6, anagent may be able to modify a rental branch and a vehicle typesubsequent to the rental vehicle being picked up. The processor 250 mayimplement the rental request process to ensure that the claim has beencreated. The processor 250 may escalate the request to an insuranceagent if the request does not comply with associated rules. Theprocessor 250 may also implement the rental request process to ensurethe current request is the next transaction to be applied to the claim(e.g., the processor 250 may wait for a prior transaction and escalatethe current request if the current request does not meet an associatedservice level agreement (SLA)). The processor 250 may implement a rentalrequest process to ensure the claim is in a valid state for rentalreservation and escalate the request to an insurance agent if therequest does not comply with associated rules. The processor 250 mayimplement a rental request process to ensure the cause of loss (COL) hasbeen created (e.g., the processor 250 may try to create the rentalautomatically or escalate the request to an insurance agent to createthe rental). The processor 250 may further implement the rental requestprocess to ensure that a rental performer is assigned to the claim(e.g., the processor 250 may try to automatically assign or escalate therequest to an insurance agent to assign the request). If a new request,the processor 250 may implement a rental request process to ensure aduplicate rental request does not exist (e.g., the processor 250 mayautomatically reconcile differences or escalate the request to aninsurance agent to resolve). If the request is an updated request, theprocessor 250 may implement the rental request process to ensure thatthe prior reservation exists and that the prior reservation is in astate to accept updates. If the processor 250 cannot determine whether aprior reservation exists, the processor 250 may escalate the request toan insurance agent. The processor 250 may implement a rental requestprocess to determine if a rental reservation or update is valid for thisclaim. The processor 250 may escalate the request to an insurance agentto resolve (e.g., if a claim was marked as duplicate, then the rental isnot valid). The processor 250 may implement a rental request process tocreate/update rental reservation. The processor 250 may implement arental request process to record the resolution of the customer's rentalrequest. The processor 250 may monitor the entire rental request processto determine how many times the rental request process must be assistedby a claim handler. The processor 250 may analyze trends foropportunities to make improvements to the process. The processor 250 maymonitor the entire process to determine a status of any given request.

The details associated with a computer system 200 for automaticallyupdating insurance related information are now described beginning withreference to FIG. 2. FIG. 2 depicts a high-level block diagram of acomputer system 200 that implements communications between a clientdevice 205 (e.g., a personal computer or a mobile telephone) and aremote computing device (e.g., server 210) to automatically provideupdated data to an insurance related database 265. The client device 205may be communicatively coupled to the remote computing device 210 via anetwork 215.

For clarity, only one client device 205 is depicted in FIG. 2. WhileFIG. 2 depicts only one client device 205, it should be understood thatany number of client devices 205 may be supported and that each clientdevice 205 may be any appropriate computing device, such as a mobiletelephone, a personal data assistant, a tablet, a desk-top computer or alap-top computer. The client device 205 may include a memory 220 and aprocessor 225 for storing and executing, respectively, a module 221. Themodule 221, stored in the memory 220 as a set of computer-readableinstructions, may be related to an insurance application that, whenexecuted on a processor 225, causes the processor 225 to receive changedata (e.g., data representative of a desired vehicle rental) from aninsurance customer via the touch input/keyboard 230 and/or the display235. As described in detail herein, the module 221 may facilitateinteraction between the client device 205 and the remote computingdevice 210.

The processor 225, further executing the module 221, may facilitatecommunications between the computing device 210 and the client device205 via a network interface 240, a client device network connection 216and the network 215. The display device 235 which may be any type ofelectronic display device such as a liquid crystal display (LCD), alight emitting diode (LED) display, a plasma display, a cathode ray tube(CRT) display, or any other type of known or suitable electronicdisplay. The touch input/keyboard/pointing device 230 (e.g., user inputdevice such as a mouse) may provide a mechanism for a user of the clientdevice 205 to launch a data entry application and to enter relatedchange information. The user input device 230 may be configured as anintegral part of a display device 235, such as a touch screen displaydevice. The network interface 240 may be configured to facilitatecommunications between the client device 205 and the remote computingdevice 210 via any hardwired or wireless communication network 215,including, for example, a hardwired Ethernet connection or a wirelessLAN, MAN or WAN, WiFi, the Internet, or any combination thereof.Moreover, the client device 205 may be communicatively connected to theremote computing device 210 via any suitable communication system, suchas via any publicly available or privately owned communication network,including those that use wireless communication structures, such aswireless communication networks, including for example, wireless LANsand WANs, satellite and cellular telephone communication systems, etc.

The computing device 210 may include a memory 245 and a processor 250for storing and executing, respectively, a module 246. The module 246,stored in the memory 245 as a set of computer-readable instructions,facilitates applications related to automatically updating insurancerelated data. The module 245 may also facilitate communications betweenthe computing device 210 and the client device 205 via a networkinterface 255, a remote computing device network connection 217 and thenetwork 215 and other functions and instructions.

The computing device 210 may be communicatively coupled to an insurancerelated database 265 and/or a business rules database 260. While theinsurance related database 265 and the business rules database are shownin FIG. 3 as being communicatively coupled to the remote computingdevice 210, it should be understood that the insurance related database265 and/or the business rules database 260 may be located withinseparate remote servers (or any other suitable computing devices)communicatively coupled to the remote computing device 210. Optionally,portions of insurance related database 265 and/or the business rulesdatabase 260 may be associated with memory modules that are separatefrom one another, such as a memory 220 of the client device 205. Thecomputer system 200 may accommodate multiple channels (e.g., mobile, webor IVR). The computer system 200 may also generate versioning of data tobe updated and business rules. Furthermore, the computer system 200 maytrack which rules cause manual review to allow business processimprovements.

Turning to FIG. 3, a block diagram 300 of a client device 305 isdepicted. The client device 305 may be similar to the client device 205of FIG. 2. The client device 305 may include an insurance applicationmodule 321, a current insurance information related data retrievalmodule 322, a data change input module 323, a change data transmissionmodule 324 and a disposition data retrieval module 325 stored on amemory 320. Implementation of the modules 321-325 may allow, forexample, an insurance customer to enter desired change data (e.g., datarepresentative of a vehicle rental request) via the client device 305.

With reference to FIG. 4, a flow diagram for a method of enteringdesired change data 400 is depicted. The method 400 may, for example, beimplemented by a processor (e.g., processor 225 of FIG. 2) executing themodules 321-325. In particular, the processor 225 may execute thecurrent insurance information related data retrieval module 322 toretrieve current data that is representative of current insurancerelated information (block 405). The processor 225 may execute the datachange input module 323 to receive change data that is representative ofchange(s) that an insurance customer wishes to make to the currentinsurance related information (block 410). The processor 225 may executethe change data transmission module 324 to transmit change data from theclient device 205 to, for example, a remote computing device (e.g.,server 210 of FIG. 2) (block 420). As described in detail below, aprocessor (e.g., processor 250) of the remote computing device 210 maygenerate disposition data representative of determinations related towhether the desired changes are determined to comply with correspondingchange rule data. In any event, the processor 225 may execute thedisposition data retrieval module 325 to retrieve disposition data(block 425). The processor 225 may further execute the disposition dataretrieval module 325 to generate a disposition report (e.g., a display)based on the disposition data (block 430).

With reference to FIG. 5, a block diagram of an example remote computingdevice (e.g., server) 510 is depicted. The remote computing device 510may be similar to the remote computing device 210 of FIG. 2. The remotecomputing device 510 may include an insurance application module 546, abusiness rules input module 547, a current data transmission module 548,a change data retrieval module 549, a change data/business rulescomparison module 550 and a disposition data transmission module 551stored on a memory 545. A processor (e.g., processor 250 of FIG. 2) mayexecute the modules 546-551 to determine disposition data based on adetermination whether at least one desire change to the currentinsurance related data complies with corresponding business rules.

With reference to FIG. 6, a flow diagram is depicted for a method ofdetermining disposition data 600. The disposition data 600 may, forexample, be indicative of whether a desired change to the currentinsurance related information complies with corresponding business rules(e.g., is a vehicle rental request valid). The processor 250 may executethe current data transmission module 548 and the processor 225 mayexecute the insurance application module 321 to present a display to aninsurance customer representative of current data (block 605). Theprocessor 250 may execute the change data retrieval module 549 toretrieve desired changes to the current insurance related information(block 605). The processor 250 may execute the business rules inputmodule 547 to retrieve business rules (e.g., rules related to vehiclerental within an insurance policy) (block 610). The processor 250 mayexecute the insurance application module 546 and the changedata/business rules comparison module 550 to automatically compare thedesired changes to the business rules to automatically decide if thechanges can be accepted, rejected or require additional review by aninsurance agent (block 615). If the processor 250 determines that thechanges do not comply with the rules (block 620), the processor 250 mayautomatically reject the changes (block 625) and generates acorresponding record of the disposition (block 630). The processor 250may further execute the disposition data transmission module 551 toautomatically transmit the disposition data to a client device 205, 305(block 630). If the processor 250 cannot determine whether the desirechanges comply with the business rules (block 620), the processor 250may automatically route the changes to an insurance agent for review(block 635). The insurance agent may review the desired changes and maymodify the desire changes (block 640). The insurance agent may thendetermine whether any desired changes, or modified changes, comply withthe business rules (block 650). If the insurance agent determines thatthe desire changes, or the modified changes, comply with the businessrules (block 650), the insurance agent may update the current insurancerelated information (block 670). If the insurance agent determines thatthe desired changes, or the modified changes, do not comply with thebusiness rules (block 650), the insurance agent may reject the changes(block 660). The insurance agent may send a disposition report to theinsurance customer that reflects the disposition (block 630). If theprocessor 250 determines that the desired changes comply with thebusiness rules (block 620), the processor 250 may automatically rejectthe desired changes (block 665) and the processor 250 may automaticallyupdate the current insurance related information (block 670). Theprocessor 250 may automatically generate a record of the disposition andsend the record to the insurance customer (block 630).

This detailed description is to be construed as exemplary only and doesnot describe every possible embodiment, as describing every possibleembodiment would be impractical, if not impossible. One could implementnumerous alternate embodiments, using either current technology ortechnology developed after the filing date of this application.

What is claimed is:
 1. A computer-implemented method for an insuredindividual to automatically determine whether a change to an insuranceclaim is available via an insurance policy of the insured individual,the method comprising: automatically receiving, by a processor of acomputing device, current valid insurance claim data in response to anaction by the insured individual, via a user input device, wherein thecurrent valid insurance claim data is representative of informationrelated to an existing valid insurance claim; automatically generating,by a processor of a computing device, a current display, on a displaydevice connected to the computing device, based on the current validinsurance claim data, wherein the display presents current validinsurance claim related information to the insured individual includinga cause of loss and an assigned vendor for correction of the loss;automatically receiving, by a processor of a computing device, currentvalid insurance claim change data from the insured individual via a userinput device, where the current valid insurance claim change data isrepresentative of desired insurance claim change information associatedwith the current valid insurance claim data, and wherein the desiredinsurance claim change information pertains to the assigned vendor;automatically receiving, by a processor of a computing device, updaterules data from an update rules data database stored on a memory of thecomputing device, wherein the update rules data is representative ofrules related to updates to the current valid insurance claim data thatare permitted by the insured individual in accordance with the insurancepolicy of the insured individual; automatically determining, by aprocessor of a computing device, whether at least one change to thecurrent valid insurance claim data is acceptable based on the currentvalid insurance claim change data and the update rules data; if the atleast one change to the current valid insurance claim data isdetermined, by the processor of the computing device, to be acceptable,the current valid insurance claim data is automatically changed, by theprocessor of the computing device, based on the current valid insuranceclaim change data and the processor automatically provides an indicationto the insured individual that the at least one change is acceptable;and if the at least one change to the current valid insurance claim datais determined, by the processor of the computing device, to not beacceptable, the current valid insurance claim data remains unchanged andthe processor automatically provides an indication to the insuredindividual that the at least one change is not acceptable.
 2. The methodof claim 1, wherein the current insurance related information isrepresentative of an insurance claim.
 3. The method of claim 1, furthercomprising: generating, using a processor of a computing device, updatedinsurance related data, based on the change data, when the processordetermines that at least one change to the current insurance relatedinformation is acceptable, wherein the updated insurance related data isrepresentative of updated insurance related information.
 4. The methodof claim 3, further comprising: generating, using a processor of acomputing device, an updated display based on the updated insurancerelated data, wherein the updated display indicates changes to thecurrent insurance related information that have been accepted.
 5. Themethod of claim 1, further comprising: generating, using a processor ofa computing device, rejection data, based on the change data, when theprocessor determines that at least one change to the current insurancerelated information is not acceptable, wherein the rejection data isrepresentative of reasons for rejection information.
 6. The method ofclaim 5, further comprising: generating, using a processor of acomputing device, a rejection display based on the rejection data,wherein the rejection display indicates at least one reason why at leastone change has been rejected.
 7. The method of claim 1, furthercomprising: generating, using a processor of a computing device,insurance agent data based on the change data when the processor isunable to determine whether, or not at least one change to the currentinsurance related information is acceptable.
 8. The method of claim 7,further comprising: generating, using a processor of a computing device,an insurance agent display based on the insurance agent data, whereinthe insurance agent display indicates that the processor was unable todetermine whether, or not at least one change is acceptable.
 9. Acomputer system for an insured individual to automatically determinewhether a change to an insurance claim is available via an insurancepolicy of the insured individual, the computer system comprising: acurrent data receiving module stored on a memory that, when executed bya processor of a computing device, causes the processor to automaticallyreceive current valid insurance claim data in response to an action bythe insured individual, via a user input device, wherein the currentvalid insurance claim data is representative of information related toan existing valid insurance claim; a current display generating modulestored on a memory that, when executed by a processor of a computingdevice, causes the processor to automatically generate a current displaybased on the current valid insurance claim data, wherein the displaypresents current valid insurance claim related information to an insuredindividual; a change data receiving module stored on a memory that, whenexecuted by a processor of a computing device, causes the processor toautomatically receive current valid insurance claim change data from theinsured individual, where the current valid insurance claim change datais representative of desired insurance claim change informationassociated with the current valid insurance claim data; an update rulesdata receiving module stored on a memory that, when executed by aprocessor of a computing device, causes the processor to automaticallyreceive update rules data, wherein the update rules data isrepresentative of rules related to updates to the current validinsurance claim related data that are permitted by the insuredindividual in accordance with the insurance policy of the insuredindividual; an acceptable change determining module stored on a memorythat, when executed by a processor of a computing device, causes theprocessor to automatically determine whether at least one change to thecurrent valid insurance claim data is acceptable based on the currentvalid insurance claim change data and the update rules data; if the atleast one change to the current valid insurance claim data isdetermined, by the processor of the computing device, to be acceptable,the current valid insurance claim data is automatically changed, by theprocessor of the computing device, based on the current valid insuranceclaim change data and the processor automatically provides an indicationto the insured individual that the at least one change is acceptable;and if the at least one change to the current valid insurance claim datais determined, by the processor of the computing device, to not beacceptable, the current valid insurance claim data remains unchanged andthe processor automatically provides an indication to the insuredindividual that the at least one change is not acceptable.
 10. Thecomputer system of claim 9, further comprising: an updated insurancerelated data generating module stored on a memory that, when executed bya processor of a computing device, causes the processor to generateupdated insurance related data, based on the change data, when theprocessor determines that at least one change to the current insurancerelated information is acceptable, wherein the updated insurance relateddata is representative of updated insurance related information.
 11. Thecomputer system of claim 10, further comprising: an updated displaygenerating module stored on a memory that, when executed by a processorof a computing device, causes the processor to generate an updateddisplay based on the updated insurance related data, wherein the updateddisplay indicates changes to the current insurance related informationthat have been accepted.
 12. The computer system of claim 9, furthercomprising: a rejection data generating module stored on a memory that,when executed by a processor of a computing device, causes the processorto generate rejection data, based on the change data, when the processordetermines that at least one change to the current insurance relatedinformation is not acceptable, wherein the rejection data isrepresentative of reasons for rejection information.
 13. The computersystem of claim 12, further comprising: a rejection display generatingmodule stored on a memory that, when executed by a processor of acomputing device, causes the processor to generate a rejection displaybased on the rejection data, wherein the rejection display indicates atleast one reason why at least one change has been rejected.
 14. Thecomputer system of claim 9, further comprising: an insurance agent datagenerating module stored on a memory that, when executed by a processorof a computing device, causes the processor to generate insurance agentdata based on the change data when the processor is unable to determinewhether, or not at least one change to the current insurance relatedinformation is acceptable.
 15. The computer system of claim 14, furthercomprising: an insurance agent display generating module stored on amemory that, when executed by a processor of a computing device, causesthe processor to generate an insurance agent display based on theinsurance agent data, wherein the insurance agent display indicates thatthe processor was unable to determine whether, or not at least onechange is acceptable.
 16. A tangible computer-readable memory storinginstructions for an insured individual to automatically determinewhether a change to an insurance claim is available via an insurancepolicy of the insured individual, the tangible computer-readable memorycomprising: a current data receiving module that, when executed by aprocessor of a computing device, causes the processor to automaticallyreceive current valid insurance claim data in response to an action bythe insured individual, via a user input device, wherein the currentvalid insurance claim data is representative of information related toan existing valid insurance claim; a current display generating modulethat, when executed by a processor of a computing device, causes theprocessor to automatically generate a current display based on thecurrent valid insurance claim data, wherein the display presents currentvalid insurance claim related information to an insured individual; achange data receiving module that, when executed by a processor of acomputing device, causes the processor to automatically receive currentvalid insurance claim change data from the insured individual, where thecurrent valid insurance claim change data is representative of desiredinsurance claim change information associated with the current validinsurance claim data; an update rules data receiving module that, whenexecuted by a processor of a computing device, causes the processor toautomatically receive update rules data, wherein the update rules datais representative of rules related to updates to the current validinsurance claim related data that are permitted by the insuredindividual in accordance with the insurance policy of the insuredindividual; an acceptable change determining module that, when executedby a processor of a computing device, causes the processor toautomatically determine whether at least one change to the current validinsurance claim data is acceptable based on the current valid insuranceclaim change data and the update rules data; if the at least one changeto the current valid insurance claim data is determined, by theprocessor of the computing device, to be acceptable, the current validinsurance claim data is automatically changed, by the processor of thecomputing device, based on the current valid insurance claim change dataand the processor automatically provides an indication to the insuredindividual that the at least one change is acceptable; and if the atleast one change to the current valid insurance claim data isdetermined, by the processor of the computing device, to not beacceptable, the current valid insurance claim data remains unchanged andthe processor automatically provides an indication to the insuredindividual that the at least one change is not acceptable.
 17. Thecomputer system of claim 16, further comprising: an updated insurancerelated data generating module that, when executed by a processor of acomputing device, causes the processor to generate updated insurancerelated data, based on the change data, when the processor determinesthat at least one change to the current insurance related information isacceptable, wherein the updated insurance related data is representativeof updated insurance related information.
 18. The computer system ofclaim 17, further comprising: an updated display generating module that,when executed by a processor of a computing device, causes the processorto generate an updated display based on the updated insurance relateddata, wherein the updated display indicates changes to the currentinsurance related information that have been accepted.
 19. The computersystem of claim 16, further comprising: a rejection data generatingmodule that, when executed by a processor of a computing device, causesthe processor to generate rejection data, based on the change data, whenthe processor determines that at least one change to the currentinsurance related information is not acceptable, wherein the rejectiondata is representative of reasons for rejection information.
 20. Thecomputer system of claim 19, further comprising: a rejection displaygenerating module that, when executed by a processor of a computingdevice, causes the processor to generate a rejection display based onthe rejection data, wherein the rejection display indicates at least onereason why at least one change has been rejected.
 21. The computersystem of claim 16, further comprising: an insurance agent datagenerating module that, when executed by a processor of a computingdevice, causes the processor to generate insurance agent data based onthe change data when the processor is unable to determine whether, ornot at least one change to the current insurance related information isacceptable.
 22. The computer system of claim 21, further comprising: aninsurance agent display generating module that, when executed by aprocessor of a computing device, causes the processor to generate aninsurance agent display based on the insurance agent data, wherein theinsurance agent display indicates that the processor was unable todetermine whether, or not at least one change is acceptable.